Internet Info 1997 December/Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso/ietf/urn/urn-archives/urn-ietf.archive.9611/000014_owner-urn-ietf _Mon Nov 4 03:20:37 1996.msg

Internet Message Format | 1997-02-19 | 2KB

Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id DAA26111 for urn-ietf-out; Mon, 4 Nov 1996 03:20:37 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id DAA26106 for <[e-mail]>; Mon, 4 Nov 1996 03:20:35 -0500
Received: from alpha.Xerox.COM by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b)
        id AA20672  (mail destined for [e-mail]); Mon, 4 Nov 96 03:20:03 -0500
Received: from golden.parc.xerox.com ([13.1.100.139]) by alpha.xerox.com with SMTP id <15465(3)>; Mon, 4 Nov 1996 00:20:01 PST
Received: by golden.parc.xerox.com id <2696>; Mon, 4 Nov 1996 00:19:43 PST
To: [e-mail]
Cc: [e-mail], [e-mail], [e-mail]
In-Reply-To: <[e-mail]> ([e-mail])
Subject: Re: [URN] HTTP resolution protocol
From: Larry Masinter <[e-mail]>
Message-Id: <96Nov4.001943pst."2696"@golden.parc.xerox.com>
Date: Mon, 4 Nov 1996 00:19:43 PST
Sender: [e-mail]
Precedence: bulk
Reply-To: Larry Masinter <[e-mail]>
Errors-To: [e-mail]

# GET service:/uri HTTP/1.1 is certainly valid.

Well,

       Request-Line   = Method SP Request-URI SP HTTP-Version CRLF
       Request-URI    = "*" | absoluteURI | abs_path

and 'service:/uri' doesn't look like an 'abs_path', so it must be an
'absoluteURI'.

While the HTTP spec doesn't explicitly limit Request-URIs to be URLs,
I think it was the intent that they be resource identifiers of some
sort. So now you're left with the idea that 'service' is really a kind
of URL/URN scheme.

You could do it, sure, and probably not break any existing HTTP
servers either, but it's really odd to think of 'N2L' as a URI
scheme, since it doesn't really locate a resource.

Larry